Skip step with no conclusion #22
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are two ways a step in a job may be skipped: - Step skipped due to an `if:` conditional: When a step has an `if:` condition that evaluates to `false`, the step is never sent to the runner for execution. In this case, the steps array in the workflow_job webhook payload will show the step, but its conclusion will be `null`. For this part we check the step.conclusion and ignore those that are not ran. - Step skipped due to a previous `step failure`: This is the case when the step is marked with conclusion 'skipped'. If a previous step fails, all subsequent steps in the same job are immediately skipped. Their conclusion will be 'skipped'. For this part we doublecheck the step duration and ignore if it is not set
ahmedelgabri
approved these changes
Sep 18, 2025
IvanKuzyshyn
approved these changes
Sep 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are two ways a step in a job may be skipped:
if:conditional: When a step has anif:condition that evaluates tofalse, the step is never sent to the runner for execution. In this case, the steps array in the workflow_job webhook payload will show the step, but its conclusion will benull.For this part we check the step.conclusion and ignore those that are not ran.
step failure: This is the case when the step is marked with conclusion 'skipped'. If a previous step fails, all subsequent steps in the same job are immediately skipped. Their conclusion will be 'skipped'.For this part we doublecheck the step duration and ignore if it is not set